From: Greg KH <gregkh@linuxfoundation.org>
To: Elizabeth Ferdman <gnudevliz@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2] staging: sm750fb: replace macro with builtin fn
Date: Sun, 9 Oct 2016 16:35:15 +0200 [thread overview]
Message-ID: <20161009143515.GA11086@kroah.com> (raw)
In-Reply-To: <20161007223250.GA2680@localhost>
On Fri, Oct 07, 2016 at 03:32:51PM -0700, Elizabeth Ferdman wrote:
> On Fri, Oct 07, 2016 at 04:59:36PM +0200, Greg KH wrote:
> > On Sun, Oct 02, 2016 at 03:33:59PM -0700, Elizabeth Ferdman wrote:
> > > Drop a local macro definition and replace its uses with a standard
> > > macro function from linux/kernel.h: DIV_ROUND_CLOSEST, to avoid
> > > reproducing code.
> > >
> > > Signed-off-by: Elizabeth Ferdman <gnudevliz@gmail.com>
> > > ---
> > > Changes in v2:
> > > - Use "with" not w in the subject line
> > > - Specify the name of the builtin macro in the description
> > > - Explain why this change is necessary
> >
> > Someone else already sent this patch in and got it accepted before you
> > did, sorry.
>
> Is there any easy way to monitor what's currently being sent? I found
> lkml.org and mail-archive.com/linux-kernel@vger.kernel.org. The latter
> is a nicer one to look at. Just wondering what you use.
lkml is not something you really need to read, it's a firehose :)
staging patches come in on the driverdevel mailing list, the address for
it is in the MAINTAINERS file. You can subscribe to it, that is the
easiest thing to do, to see what is also being sent at the same time.
thanks,
greg k-h
prev parent reply other threads:[~2016-10-09 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 22:33 [PATCH v2] staging: sm750fb: replace macro with builtin fn Elizabeth Ferdman
2016-10-07 14:59 ` Greg KH
2016-10-07 22:32 ` Elizabeth Ferdman
2016-10-09 14:35 ` Greg KH [this message]
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=20161009143515.GA11086@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gnudevliz@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
/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.