All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Thomas Davies <daviesth@onid.orst.edu>
Cc: kernel-janitors@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [KJ] [PATCH] fix warnings that occur on make *docs
Date: Thu, 01 Mar 2007 21:44:29 +0000	[thread overview]
Message-ID: <45E7493D.2040104@oracle.com> (raw)
In-Reply-To: <953c67830703011338n6c9c6b8wafe68b6af6b974b1@mail.gmail.com>

Thomas Davies wrote:
> On 3/1/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> On Thu, 1 Mar 2007 10:39:41 -0800 Thomas Davies wrote:
>>
>> > From: Thomas Davies <daviesth@onid.orst.edu>
>> >
>> > Cleaned up comments and whitespace in /drivers/message/fusion/*.c 
>> and also
>> > /lib/bitmap.c to remove make *docs warnings.  An attempt by a newbie
>> > to contribute
>> > in some small way to the codebase.  Did I do it right?
>>
>> Hi,
>>
>> Your patch looks fine (until I tested it), but I have already
>> corrected these warnings.  The patches have been in the -mm patchset
>> for awhile and Andrew has sent some of it to Linus to be merged.
>> Other parts need to go thru other maintainers.
> 
> Thank you for the feedback Randy.  Looks like I missed a step in the cycle;
> I cloned Linus' tree with git from
> git://git.kernel.org/pub/[...]/torvalds/linux-2.6.git,
> was this wrong?  Is there another tree I should be cloning, or do I
> apply the -mm
> patch from kernel.org before making this sort of change? (The latter I 
> suspect.)

I don't think that my patches have been merged by Linus yet (sent by
Andrew, but there must be some delay there :) .

To see if anything has already been patched, it often takes reviewing
both Linus's tree and Andrew's -mm patches.  Hopefully we don't also
need to review all gits of all maintainers, since Andrew tries to
merge all of those into the -mm patchset.

>> > Signed-off-by: Thomas Davies <daviesth@onid.orst.edu>
>> > ---
>> > diff -uprN -X linux-2.6/Documentation/dontdiff
>> > linux-2.6/drivers/message/fusion/mptbase.c
>> > linux-2.6-new/drivers/message/fusion/mptbase.c
>>
>> Looks like your mail client split these lines (above and below)
>> so that 'patch' cannot apply the patch.
>> lkml.org shows the same splitting, so I guess it's not my
>> mail client on the reading end that is doing this.
> 
> I thought I could get away with using gmail in plain text mode, guess
> I'll go back to using mutt.

gmail works if you use the SMTP interface to it (or probably with
attachments, but they aren't good for reviews/reviewers).
Yes, mutt works.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Thomas Davies <daviesth@onid.orst.edu>
Cc: kernel-janitors@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix warnings that occur on make *docs
Date: Thu, 01 Mar 2007 13:44:29 -0800	[thread overview]
Message-ID: <45E7493D.2040104@oracle.com> (raw)
In-Reply-To: <953c67830703011338n6c9c6b8wafe68b6af6b974b1@mail.gmail.com>

Thomas Davies wrote:
> On 3/1/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> On Thu, 1 Mar 2007 10:39:41 -0800 Thomas Davies wrote:
>>
>> > From: Thomas Davies <daviesth@onid.orst.edu>
>> >
>> > Cleaned up comments and whitespace in /drivers/message/fusion/*.c 
>> and also
>> > /lib/bitmap.c to remove make *docs warnings.  An attempt by a newbie
>> > to contribute
>> > in some small way to the codebase.  Did I do it right?
>>
>> Hi,
>>
>> Your patch looks fine (until I tested it), but I have already
>> corrected these warnings.  The patches have been in the -mm patchset
>> for awhile and Andrew has sent some of it to Linus to be merged.
>> Other parts need to go thru other maintainers.
> 
> Thank you for the feedback Randy.  Looks like I missed a step in the cycle;
> I cloned Linus' tree with git from
> git://git.kernel.org/pub/[...]/torvalds/linux-2.6.git,
> was this wrong?  Is there another tree I should be cloning, or do I
> apply the -mm
> patch from kernel.org before making this sort of change? (The latter I 
> suspect.)

I don't think that my patches have been merged by Linus yet (sent by
Andrew, but there must be some delay there :) .

To see if anything has already been patched, it often takes reviewing
both Linus's tree and Andrew's -mm patches.  Hopefully we don't also
need to review all gits of all maintainers, since Andrew tries to
merge all of those into the -mm patchset.

>> > Signed-off-by: Thomas Davies <daviesth@onid.orst.edu>
>> > ---
>> > diff -uprN -X linux-2.6/Documentation/dontdiff
>> > linux-2.6/drivers/message/fusion/mptbase.c
>> > linux-2.6-new/drivers/message/fusion/mptbase.c
>>
>> Looks like your mail client split these lines (above and below)
>> so that 'patch' cannot apply the patch.
>> lkml.org shows the same splitting, so I guess it's not my
>> mail client on the reading end that is doing this.
> 
> I thought I could get away with using gmail in plain text mode, guess
> I'll go back to using mutt.

gmail works if you use the SMTP interface to it (or probably with
attachments, but they aren't good for reviews/reviewers).
Yes, mutt works.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-03-01 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 18:39 [KJ] [PATCH] fix warnings that occur on make *docs Thomas Davies
2007-03-01 18:39 ` Thomas Davies
2007-03-01 18:49 ` [KJ] " Randy Dunlap
2007-03-01 18:49   ` Randy Dunlap
2007-03-01 21:38   ` [KJ] " Thomas Davies
2007-03-01 21:38     ` Thomas Davies
2007-03-01 21:44     ` Randy Dunlap [this message]
2007-03-01 21:44       ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45E7493D.2040104@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=daviesth@onid.orst.edu \
    --cc=kernel-janitors@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.