Dear Stefano Babic,
In message 1286875504-9058-2-git-send-email-sbabic@denx.de you wrote:
The patch adds the linux framebuffer header file. As several drivers are ported from Linux, it is easier to reuse the same structures already present in the kernel.
Signed-off-by: Stefano Babic sbabic@denx.de
include/linux/fb.h | 616 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 616 insertions(+), 0 deletions(-) create mode 100644 include/linux/fb.h
Please include an indication where exactly the code is coming from, as described in the Linux kernel's "SubmittingPatches" document:
| Special note to back-porters: It seems to be a common and useful practise | to insert an indication of the origin of a patch at the top of the commit | message (just after the subject line) to facilitate tracking. For instance, | here's what we see in 2.6-stable : | | Date: Tue May 13 19:10:30 2008 +0000 | | SCSI: libiscsi regression in 2.6.25: fix nop timer handling | | commit 4cf1043593db6a337f10e006c23c69e5fc93e722 upstream | | And here's what appears in 2.4 : | | Date: Tue May 13 22:12:27 2008 +0200 | | wireless, airo: waitbusy() won't delay | | [backport of 2.6 commit b7acbdfbd1f277c1eb23f344f899cfa4cd0bf36a] | | Whatever the format, this information provides a valuable help to people | tracking your trees, and to people trying to trouble-shoot bugs in your | tree.
So please include at least the name of the file in the Linux tree and the exact kenrel version used as a reference in the commit message.
Thanks.
Best regards,
Wolfgang Denk